fix: deserialize Id-suffixed tracking option keys - #813
Open
miachillgood wants to merge 1 commit into
Open
Conversation
miachillgood
force-pushed
the
fix/deserialize-id-suffix-variants
branch
from
August 8, 2026 00:14
93bd8b3 to
4105b25
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
...IDto...IdkeysTrackingOptionIdinside invoice line-item tracking dataWhy
#777reports thattrackingOptionIDis defined in the SDK types but stays undefined whengetInvoices()returns tracking data.The generated accounting deserializer currently only reads exact
...IDkeys. When the API response uses an...Idvariant, the value is dropped during deserialization.Testing
npm test -- --runInBand src/test/objectSerializer.spec.tsnpm run buildCloses #777